Catch up on stories from the past week (and beyond) at the Slashdot story archive

typodupeerror

CommentRe:How expensive could it possibly be to run uber? (Score 4, Interesting)190

They aren't charging enough on fares to keep their company and the drivers running. They've tried to become more sustainable by trimming driver payments, but it's still not enough. Even with a limited monopoly, taxi companies weren't incredible profit generators. The main reason Uber and Lyft are cheaper is that they're being subsidized by investors to try to get enough of a market dominance they can then increase prices.

CommentRe:Translation (Score 1)382

Neither can Tesla, right now. Tesla is promising full autonomous driving, but it isn't there yet. It also has lost features from the original AP1 hardware (reliable automatic windshield wipers) that it has not yet replicated with AP2, because it's relying on different hardware and software to enable it.

Tesla is really betting on "software will fix everything", but there's really no saying when it'll happen.

CommentRe:Of course they aren't (Score 3, Interesting)87

How likely is it that they will catch the people who did it? And if they do, how likely is that to reduce the chances of someone else doing the same thing?

If someone steals your car, you contact the cops because it's possible you'll get your car back. Even if not, it's sort of possible they'll find the car thief, because the city is only so big. But finding who put ransomware on your computer among billions of people all over the world?

Again, there's nothing in it for the victim.

CommentRe:What the hell is "rust"? (Score 3, Insightful)236

The Accidental Tech Podcast had an interview with Chris Lattner where he discussed the future of Swift as a systems language and compared it to Rust. Rust has a very upfront memory ownership model that requires programmers to be explicit about memory management. This allows Rust to have great performance and allows the compiler to ensure memory is used safely that is not an option with C.

With Swift, either you pretty much don't think about memory (it uses Automatic Reference Counting so you only need to care about cycles), or you need to go down to C-style memory semantics with the various Unsafe constructions. There are cases where you could get much better performance because the programmer knows the lifecycle of the objects being used, but that can't currently be expressed in Swift. It can be expressed in Rust.

To be a good systems programming language, Chris said that Swift will need to create a memory ownership model (and mentioned Rust as having ideas that might apply). He would like that ownership model to be opt-in for specific pieces of your code that require it: most people could use ARC, while people that need performance in a specific piece could be more detailed about the memory management. It's on his list of things that Swift will acquire over the years so it can achieve world domination.

So there are really pretty good reasons that Mozilla put together Rust. The browser is probably the most widely exposed attack surface right now, and the history of buffer overloads means there needed to be a safer way to code.

Slashdot Top Deals

"We live, in a very kooky time." -- Herb Blashtfalt

Working...
close